1.If you are interested in setting up the UCM use model for your configuration management, proceed to the next section.
如果您对为配置管理创建UCM使用模型，继续学习接下来的章节。
2.After modeling, we use model checker to check some of its key properties, which can guarantee the system's correctness and reliability.
建模后利用已经开发的模型检测工具，检测系统的一些重要性质可以保证系统的可靠性和正确性。
3.UCM was developed to make it much easier for people using ClearCase to get started with an effective use model.
UCM被发展出来，使得人们从一个有效的使用模型开始使用ClearCase变得更容易了。
4.Let's start our discussion of libvirt with a view of the use model, then dig into its architecture and use.
首先让我们从用例模型视角来展开对libvirt的讨论，然后深入探究其架构和用途。
5.OPERATOR plans to use MODEL SITE PRICES, however, on some occasions a planned SITE may be very much different than a model site.
运营商计划使用模型站点价格，但有些时候计划完成的站点与模型站点会有很大不同。
6.The calculated results use model in cylindrical coordinate are compared with the results use model in rectangular coordinate.
最后将文中的计算结果与采用传统直角坐标模型计算所得结果进行了比较。
7.Rails migrations let you use model logic with your data migration where SQL scripts don't.
Rails迁移支持把模型逻辑用于数据迁移，而SQL脚本做不到这一点。
8.You use model state - or more accurately, the model state dictionary - to represent validation errors.
使用模型状态，或是更精密的模型状态字典，用来表现验证错误。
9.The second part makes a comparison of the ownership model and the right-to-use model.
第二部分将所有权模式和使用权模式的分时享有制度进行比较。
10.Listing 9 provides the output for this use model (but in this case, some of the output has been pruned for brevity).
清单9给出这个使用模型的输出（为了简短，这里删除了一些输出）。